Skip to content

Conversation

@bradmesserle
Copy link

Name of feature:

Pain or issue this feature alleviates:

Why is this important to the project (if not answered above):

Is there documentation on how to use this feature? If so, where?

In what environments or workflows is this feature supported?

In what environments or workflows is this feature explicitly NOT supported (if any)?

Supporting links/other PRs/issues: 304

I dont know if it is my environment because i have all the latest go code and kubernetes, but when the you apply the ClusterIssuer crd the CABundle gets encoded so the call to verify the providers fails. That call is expecting CABundle to be x509 PEM format. The manager fails to start.

💔Thank you!

@bradmesserle bradmesserle requested review from a team and maraino as code owners October 12, 2025 20:46
@CLAassistant
Copy link

CLAassistant commented Oct 12, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ bradmesserle
❌ Bradley Messerle


Bradley Messerle seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@github-actions github-actions bot added the needs triage Waiting for discussion / prioritization by team label Oct 12, 2025
@bradmesserle
Copy link
Author

Updated step-issuer controller also and i was able to sign a cert.

@bradmesserle
Copy link
Author

bradmesserle commented Oct 13, 2025

I sort of think that the cert should just be in configMap.. Then we have the cert in 1 place instead of 2. IMHO. but then i am not an expert at kubernetes..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs triage Waiting for discussion / prioritization by team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants